Overview

This article lists the log files commonly referenced for troubleshooting issues.

Information

Apache Error Log

• Description:
  This is the place where Apache HTTPD will send diagnostic information and record any errors that it encounters in processing requests.
• Server type:
  Application Server
• Log File Location:
  /usr/local/jive/var/logs/httpd-error.log

Apache Access Log

• Description:
  The server access log records all requests processed by the server. The jive-httpd-access.log file is the Apache HTTP server log, which contains a list of all web requests coming into the Jive application. This is very useful for detecting problems with web resource loading (i.e. CSS, JavaScript, API calls, etc.). These tools will help you understand the fine-grained details of performance and functional problems at an HTTP level.
• Server type:
  Application Server
• Log File Location:
  /usr/local/jive/var/logs/jive-httpd-access.log

Appmarket Log

• Description:
  Contains logging information related to communication with the apps market.
• Server type:
  Application Server
• Log File Location:
  /usr/local/jive/var/logs/sbs-appmarket-poll.log
/usr/local/jive/var/logs/sbs-appmarket-push.log

Docverse/Docconvert Log

• Description:
  Contains logging related to the document conversion process.
• Server type:
  Application Server
• Log File Location:
  /usr/local/jive/var/logs/sbs-docverse.log
/usr/local/jive/var/logs/docconverter-container.log
/usr/local/jive/var/logs/docconverter.out

Latency and Profiling Log

• Description:
  Some profiling options in Jive log to these files. However, the settings must be enabled, so typically, these files are empty.
• Server type:
  Application Server
• Log File Location:
  /usr/local/jive/var/logs/sbs-latency.log
/usr/local/jive/var/logs/sbs-profiling.log

Social Business Software Log

• Description:
  The sbs.log file is helpful to see any errors logged by the Jive application. If there are errors being captured in these logs then the support team may be able to use these to determine how to address the issue. The errors may also suggest that the performance issues are being caused by another resource, like low disk space, database connectivity, etc.
• Server type:
  Application Server
• Log File Location:
  /usr/local/jive/var/logs/sbs.log

Session Log

• Description:
  Contains some logging information regarding when users log in and the number of active user sessions.
• Server type:
  Application Server
• Log File Location:
  /usr/local/jive/var/logs/sbs-session.log

Cache Log

• Description:
  Contains Cache Server logs
• Server type:
  Cache Server
• Log File Location:
  /usr/local/jive/var/logs/cache.log
/usr/local/jive/var/logs/cache-service.log

Search Log

• Description:
  Contains all Search Server related logs
• Server type:
  Search Server
• Log File Location:
  /usr/local/jive/var/logs/search/service.log

Enterprise Activity Engine Log

• Description:
  Contains all EAE Server related logs
• Server type:
  EAE Server
• Log File Location:
  /usr/local/jive/var/logs/eae-service.log
/usr/local/jive/var/logs/eae-service.out